## Problem

Describe the purpose of this change. What problem is being solved and
why?

## Solution

Describe the approach you took. Link to any relevant bugs, issues, docs,
or other resources.

## Type of Change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
- [ ] Infrastructure change (CI configs, etc)
- [ ] Non-code change (docs, etc)
- [ ] None of the above: (explain here)

## Test Plan

Describe specific steps for validating this change.

## Problem

First pass implementation of control plane SDK for repositories.

Also includes a basic data plane impl that avoids using the OpenAPI
generated types due to Document being such an open-ended type. More work
is needed here


```python
pc = Pinecone(api_key=os.getenv("PINECONE_API_KEY"))

repo_name = "aryn-parsed-example-8"

repo_model = pc.create_repository(
    name=f"{repo_name}",
    spec={
        "serverless": {
            "cloud": "aws",
            "region": "us-east-1",
        },
    },
    schema={
        "fields": {
            "$.parsed[*].text_representation": {
                "description": "Text representation of the chunk",
                "embedded": True,
            },
        },
    },
    timeout=300,
)

repo_model = pc.describe_repository(name=repo_name)

# data plane
repo = pc.Repository(host=repo_model.host)

document = get_document()
response = repo.upsert(
    namespace="foo",
    document=document,
    echo=True,
)

pc.delete_repository(name=repo_name, timeout=300)
```

    


## Solution

Describe the approach you took. Link to any relevant bugs, issues, docs,
or other resources.

## Type of Change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
- [ ] Infrastructure change (CI configs, etc)
- [ ] Non-code change (docs, etc)
- [ ] None of the above: (explain here)

## Test Plan

Describe specific steps for validating this change.

---------

Co-authored-by: rohanshah18 <rohan.s@pinecone.io>

## Problem

See this notebook for usage: 

https://colab.research.google.com/drive/1aSgSZ2iQYXfkPuE9fyZiKcXxKlZxD9bq?usp=sharing

Most of this PR is generated code from the [API
spec](pinecone-io/apis#376).

### Non-generated code is here:
<img width="570" height="440" alt="Screenshot 2025-10-01 at 11 51 12 AM"
src="https://github.com/user-attachments/assets/411329f2-2cb7-4717-97c6-413e07915864"
/>








### Type of Change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [X] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [X] This change requires a documentation update
- [ ] Infrastructure change (CI configs, etc)
- [ ] Non-code change (docs, etc)
- [ ] None of the above: (explain here)


## Test Plan

Manual testing.

There are no automated tests yet. I'm hesitant to invest too heavily in
tests while there is still so much potential for things to change on the
server.

---------

Co-authored-by: rohanshah18 <rohan.s@pinecone.io>